Win Image Driver Integrator

DISM engine — User guide

Version 1.0 • Jay-R Barrios • jayrbarrios.com

Disclaimer. This application is developed by an individual and is not an official tool of, nor affiliated with or endorsed by, any hardware vendor (Dell, HP, Lenovo, Microsoft, etc.). Its purpose is to assist with integrating driver packs into Windows 10 and Windows 11 builds for demonstration and lab use. It may be applied to production images provided they go through your organisation’s proper testing and certification process. The software is provided “as is”, without warranty of any kind, express or implied; use it at your own risk. It is free to use and best suited to lab environments and demo machines. It is maintained by the developer, Jay-R Barrios (www.jayrbarrios.com), on a best-effort basis, with no guarantee of updates, fixes, or support.

1. What it does

Win Image Driver Integrator builds deployment-ready Windows images with the right drivers baked in. It takes driver packs — Dell Family Driver Packs automatically, or extracted HP / Lenovo / Surface packs — and injects them, using DISM, into either an offline Windows image (WIM/ESD) or a Windows installation ISO, extracting the ISO, injecting the drivers, and rebuilding a fresh bootable ISO.

It can also provision the image for demo and lab use: create a local administrator account, bypass OOBE, set a default wallpaper, deploy BGInfo, and apply regional settings — all in the same build.

2. Requirements

Run the app on a Windows 10/11 64-bit machine with local administrator rights (it self-elevates via UAC on launch). Use Help → System requirements at any time to re-check the environment.

Component	Needed for	Notes
.NET Framework 4.8+	Running the app	Built into Windows 10 (1903+) and Windows 11.
DISM	All injection	Built into Windows — no install required.
Windows ADK — Deployment Tools	Building bootable ISOs	Provides `oscdimg.exe`. Install separately. Offline-WIM injection works without it.
Rufus	Writing the ISO to USB	Use NTFS + GPT + UEFI (non-CSM).

Match the servicing host to the image. WinIDI uses the host’s built-in DISM, which can only service a Windows image that is the same version as, or older than, the host. Build on a machine whose Windows is at least as new as the image you’re injecting into (e.g. service 24H2 from a 24H2+ host). Servicing a newer image from an older host fails with “requires the latest version of the DISM”; the fix is a newer host, or install the matching Windows ADK and run from its Deployment Tools. Keeping the ADK current is good hygiene regardless.

3. Features

Driver sources: online Dell catalog (KB000180534) with feature-update labels (24H2 / 25H2) and a search filter, or local .zip / .cab / folder.
Detect (optional): the online list loads with nothing pre-ticked; click the Detect button any time to tick the pack matching this machine.
Targets: offline image (WIM/ESD) or ISO (extract → inject → rebuild bootable ISO).
Edition picker: reads the editions from the image; inject one or more.
Provisioning: local admin account, OOBE bypass, auto sign-in, regional/keyboard, default wallpaper, and BGInfo.
Resumable downloads that survive Wi-Fi drops, with a cached .zip so re-builds skip the download.
Automatic cleanup of temporary folders after each build (the .zip cache is kept).
Output ISO auto-named Windows_<version>-Build-<timestamp>.iso, or choose your own with Output…

4. How to use

Build a driver-injected bootable ISO

Driver packs: choose Online or Local. The online list starts empty — tick the pack(s) you need, optionally click Detect to auto-tick this machine’s model, or type in the search box (for example, 25H2) to filter.
Inject into: choose ISO file, then SELECT your base Windows ISO. Tick the edition(s) to inject (for example, Windows 11 Pro). Match the ISO’s feature update to the pack.
Optional: click Provisioning… to enable and configure DemoAdmin, OOBE bypass, wallpaper, and BGInfo.
Optional: click Output… to name or relocate the ISO; otherwise it is auto-named.
Click START and confirm. The tool mounts the ISO, exports the selected edition(s), injects the drivers, applies provisioning, rebuilds the ISO, and cleans up.
Write the finished ISO to USB with Rufus (NTFS, GPT, UEFI non-CSM).

Inject into an offline image (WIM / ESD)

Inject into: choose Offline image, then SELECT the install.wim / install.esd.
Tick the edition(s) to service, then click START. Provisioning (account, wallpaper, BGInfo) is written into the image; no ISO is produced.

Layer more drivers later

A finished output ISO can be fed back in as the source to add more drivers — injection is additive and the existing driver store is preserved. Each pass is auto-named, so nothing is overwritten.

Best practice: build from a fresh Windows ISO/WIM each time rather than feeding a previously-built ISO back in. Re-used ISOs carry read-only files that can interrupt the rebuild (the app now clears read-only on the staging contents before writing, but a fresh source is cleaner). Downloaded driver packs are cached, so starting fresh costs only build time, not another download.

5. Provisioning options

Open with the Provisioning… menu. A check mark on the menu shows it is enabled. Settings apply to ISO and offline-image builds.

A no-password administrator account is for demo / lab use only — it is not a production posture.

Local admin account: creates the account (default DemoAdmin) in the Administrators group, optionally with no password and auto sign-in.
Bypass OOBE: skips the out-of-box setup screens and goes straight to the desktop.
Regional / keyboard: sets locale and keyboard. The UI language stays en-US unless a language pack is added.
Default wallpaper: must be a JPG, minimum 1920×1080 (3840×2160 recommended) — the app rejects other formats and low-resolution images. It becomes the system default theme wallpaper (replaces img0.jpg) and turns off the Windows Spotlight desktop rotation that otherwise overrides any static wallpaper, so the image displays even before Windows is activated, yet stays fully changeable — not a locking policy, so no “managed by your organization” banner.
BGInfo: copies your BGInfo folder to C:\BGInfo and adds a launcher to the all-users Startup folder so it paints the desktop at every logon. Point it at the folder that directly contains Bginfo64.exe and the .bgi config.

6. Driver pack sources

The DISM core is vendor-blind — it injects any folder of .INF drivers. Dell packs download automatically; for other vendors, download the pack, extract it yourself, then point the app at the extracted folder.

Vendor	Driver pack	Get it & extract
Dell	Family Driver Packs (`.cab`/`.zip`)	Auto-downloaded & extracted by the app — just pick your model. No manual step.
HP	SoftPaq `.exe` (INF-based)	HP Driver Pack matrix → double-click the SoftPaq to extract → point the app at the folder.
Lenovo	SCCM/MDT pack `.exe` (by machine type)	Lenovo SCCM/MDT index → run the `.exe` to extract → point to the folder. Choose the full pack, not the NVIDIA-only one.
Microsoft Surface	Per-model `.msi` (drivers + firmware)	Surface driver/firmware page → extract with `msiexec /a file.msi /qn TARGETDIR=C:\extracted` → point to the folder.
Acer / Asus	Individual per-model drivers (no consolidated pack)	Download from the vendor support site, gather the extracted `.INF` drivers into one folder, then point the app at it.

Tip: keep only the OS-matching subfolder (e.g. the Windows 11 / x64 set) to keep the image lean and the build fast.

7. Troubleshooting

Symptom	Fix
“oscdimg.exe not found”	Install the Windows ADK ‘Deployment Tools’. Offline-WIM injection still works without it.
Boot loop on install	Match the ISO’s feature update to the pack, and in BIOS set storage to AHCI (disable VMD) if Setup can’t see the disk. Check `C:\Windows\Panther\setuperr.log`.
USB won’t boot	Write with Rufus using NTFS (install.wim exceeds the FAT32 4 GB limit), GPT, UEFI (non-CSM).
“Windows protected your PC”	The exe is unsigned. Click More info → Run anyway.
OOBE still prompts on 25H2	Newer builds tightened OOBE; if the bypass is incomplete, request the BypassNRO option.

This guide lives in the Help folder beside the app and can be edited without rebuilding. The app renders it in its own window using the built-in Windows web component — no Word or browser required.